Telephone number simplification for voip networks

ABSTRACT

A telecommunications network includes a network service computing device and a host routing device. The host routing device includes a switch. The host routing device is coupled with a remote network and a PSTN. The remote network is coupled to a plurality of communication devices. The network service computing device is in communication with a database. The database includes a plurality of tags associated with VoIP lines. The tags identify the physical location where a plurality of VoIP lines are being operated. The tags determine routing and billing of calls made from each of the VoIP lines. Using a tag as a main routing identifier, instead of just an actual phone number, increases the probability that calls made from the VoIP line are properly routed and correctly billed through the telecommunications network.

TECHNICAL FIELD

Aspects of the present disclosure generally relate to communicationnetworks; and more particularly, to systems and methods for routingvoice over Internet protocol (VoIP) network calls to and from acommunication device using one or more network routing devices.

BACKGROUND

Modern phone lines are being upgraded from analog circuits in increasingnumbers to voice over Internet protocol (VoIP). VoIP is a technologythat allows a caller to make voice calls using a broadband Internetconnection instead of a conventional (or analog) phone line. VoIPservices convert voice audio into digital signals that travel over anetwork, which may often include segments considered part of theInternet. When calling a regular phone number from a VoIP number, thesignal is converted to a regular telephone signal before it reaches thedestination. VoIP calls can be made directly from a computer, a specialVoIP phone, or a traditional phone connected to an adapter. In addition,wireless “hot spots” in locations such as airports, parks, and cafeswith connection to the Internet may enable use of VoIP servicewirelessly.

With its portability, cost savings, and the promise of enhancedfunctionality, VoIP telephony is becoming the de facto choice in manyapplications. VoIP has a range of advantages. It is a flexiblecommunication system. For example, an end user assigned a VoIP lineassociated with a New York telephone number can move to a differentstate, e.g., Colorado, and still receive calls to the same New Yorktelephone number associated with the VoIP line despite the end userphysically relocating to Colorado. As such, the VoIP telephone numbercan travel with the end user such that the end user can be accessiblevia a single VoIP telephone number at multiple locations.

However, the virtual nature and portability of VoIP can cause variousissues in the context of call routing, billing, and regulationscompliance. Specifically, conventional systems route VoIP calls throughtelecommunication networks based upon the VoIP telephone number itself,i.e., the ten digit phone number (in the United States) and as such areill equipped to route and process VoIP calls when end users operate VoIPlines outside of the geographical areas associated with the respectiveVoIP telephone numbers.

Accordingly, a need exists for improved routing devices and systems toaddress the portability of VoIP, among other improvements. It is withthese observations in mind, among others, that various aspects of thepresent disclosure were conceived and developed.

SUMMARY

A need exists for improved telecommunication systems that facilitateefficient call routing in VoIP networks. Implementations described andclaimed herein address the foregoing problems, among others, byproviding systems, methods, and devices for assigning a plurality oftags or the like to the VoIP calls, with the tags including validgeographic information about the caller and recipient of the VoIP callsfor purposes of improved call routing in a telecommunications network.Accordingly, one implementation of the present disclosure may take theform of a method of call routing for Voice over Internet Protocol (VoIP)calls, comprising utilizing a network service computing devicecomprising at least one memory for storing instructions that areexecuted by at least one processor to perform the operations of:receiving a first location associated with a first VoIP line, the firstVoIP line including a telephone number associated with the first VoIPline; creating a first tag associated with the first location, the firsttag including geographical information associated with the firstlocation to facilitate routing functionality for calls made from thefirst VoIP by the geographic information instead of routing calls fromthe first VoIP line by the telephone number; receiving a request tofacilitate a VoIP call between the first VoIP line and a second VoIPline; and routing the VoIP call using the first tag by a host routingdevice coupled to the network service computing device.

Yet another implementation of the present disclosure may take the formof a telecommunications routing system for routing VoIP calls over ahost network. The telecommunications system comprises a host routingdevice. The telecommunications system further comprises a networkservice computing device coupled to the host routing device, the networkservice computing device comprising at least one memory for storinginstructions that are executed by at least on processor to: receive afirst location associated with a first VoIP line; create a first tag forthe first VoIP line based upon the first location; wherein calls arerouted from the first VoIP line based on the first tag.

Yet another implementation of the present disclosure may take the formof a method of call routing for Voice over Internet Protocol (VoIP)calls, comprising: utilizing a network service computing devicecomprising at least one memory for storing instructions that areexecuted by at least one processor to perform the operations of:receiving a first location associated with a first VoIP line; andgenerating a first tag associated with the first location to specifyrouting functionality for calls made from the first VoIP line.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other objects, features, and advantages of the presentdisclosure set forth herein should be apparent from the followingdescription of particular embodiments of those inventive concepts, asillustrated in the accompanying drawings. The drawings depict onlytypical embodiments of the present disclosure and, therefore, are not tobe considered limiting in scope.

FIG. 1 illustrates an exemplary system view of a telecommunicationsrouting system, according to aspects of the present disclosure.

FIG. 2 illustrates an exemplary portion of a database comprising aplurality of tags and associated information for improved routing ofVoIP calls, according to aspects of the present disclosure.

FIG. 3 illustrates exemplary signaling information for VoIP calls usingthe tags, according to aspects of the present disclosure.

FIG. 4 illustrates routing functionality for VoIP calls using the tags,according to aspects of the present disclosure.

FIG. 5 illustrates an exemplary process flow for assigning and modifyingtags to a plurality of VoIP lines in a VoIP network, according toaspects of the present disclosure.

FIG. 6 illustrates an exemplary process flow for routing calls through aVoIP network using tags, according to aspects of the present disclosure.

FIG. 7 illustrates an example of a computing system that may implementvarious services, systems, and methods discussed herein.

DETAILED DESCRIPTION

Aspects of the present disclosure include systems, methods, and devicesfor assigning a plurality of tags or the like to the VoIP calls, withthe tags including valid geographic information about the caller andrecipient of the VoIP calls for purposes of improved call routing in atelecommunications network using at least one host routing device in aVoIP network. The host routing device is coupled with a remote networkand a public switched telecommunications network (PSTN). The hostrouting device may be coupled to an application server and at least onedatabase which may include a plurality of tags associated with VoIPlines. The tags identify the physical location of a VoIP device and userutilizing a given VoIP line and are used to determine routing andbilling of calls from the VoIP line. Using a tag as a main routingidentifier, to enhance or possibly replace an actual phone number,enhances the ability to properly route and correctly bill calls madefrom the VoIP lines when a call is being initiated from a differentjurisdiction than the number is otherwise associated.

A telecommunications network may include one or more national networksformed from or otherwise using one or more public and/or privatenetworks over which calls traverse between a source (the device fromwhich a caller initiates a call) and a destination (the device beingcalled and associated with a recipient). The telecommunications networkallows end users to communicate by establishing temporary communicationpathways across the network. In a telecommunications network, a publicswitched telecommunications network (PSTN) is a collection of fixedinterconnected circuit-switched networks. In the United States, the PSTNhas approximately 150 local access and transport area (LATA) networks,interconnected by networks that are known as interexchange carrier (IC)or long-distance networks. Trunks and trunk groups interconnect LATA andIC networks. Further, private networks interact with the PSTN in orderto access the networks within the PSTN.

In order to initiate a call between a source and a destination (e.g., acaller and a recipient), a communication pathway, trunk, and/or circuitmust be temporarily established between the end points of the call.Conventional telecommunication networks route calls using the actualphone number of the caller, namely, the phone number derived from theNorth American Numbering Plan (NANP). Under the NANP, a U.S. telephonenumber consist of ten digits: a three-digit area code, followed by aseven digit number. The seven digit number generally includes anexchange code identifying a telecommunications exchange within anumbering area, followed by a line number. The leading three digitnumber, commonly referred to as the “area code,” defines a state orportion of a state or a numbering plan area (NPA). Importantly, theterritory of an NPA is not identical to the service area of a LATA.Thus, depending on the actual phone number associated with the caller,the communication circuit may involve routing the call from the callerto the recipient across one or more exchanges and LATA boundaries, evenif the caller and recipient are located in the same state.

A conventional telephone, sometimes colloquially referred to as a “landline,” is confined to a specific physical location. Calls can beeffectively routed from (and billed to) a conventional telephone basedupon a NANP telephone number because the NANP telephone number includesinformation about and is specifically associated with the specificphysical location of the caller. Put simply, with analog phones,conventional systems can easily identify where the caller is located forpurposes of routing and billing the call.

In contrast, VoIP lines are not confined to specific physical locations.Users of a VoIP network can access and operate VoIP lines in multiplelocations while still maintaining the same telephone numbers assigned tothe VoIP lines. For example, a caller can initiate calls from a VoIPline, associated with a New York NANP telephone number, despite thecaller being located in Colorado. Such portability is highly beneficialto the caller and more and more users of VoIP networks wish to maintainthe same NANP telephone number when moving to different locations.

However, the portability of VoIP generates complexities and variousdrawbacks. For example, with conventional telecommunication systems,calls sent from a first VoIP line assigned a New York telephone number,are routed and/or billed across the telecommunication network based uponthe New York telephone number—even if such calls originate fromColorado, thereby creating routing inefficiencies, possible billingdifficulties, and potential compliance difficulties. The example abovecan be further illustrated in the context of local Colorado calls madefrom the first VoIP line (assigned the New York telephone number). Inone case, local Colorado calls made from the first VoIP line may berouted inefficiently, e.g., through New York, because the conventionalnetwork would be unable to recognize that the call should be a localcall. Moreover, even if the calls were routed properly between thecaller and recipient (via a local trunk), the calls would be designatedas “long-distance” or “inter-LATA” calls and the calls may still bebilled based upon the New York NANP telephone number (despite thenetwork not having to establish a long-distance communication pathbetween the caller and recipient). Accordingly, a need exists forimproved routing of VoIP calls.

For a detailed description of an example telecommunications routingsystem 100 for improving the routing of VoIP calls, reference is made toFIG. 1. Specifically, FIG. 1 illustrates a telecommunication routingsystem 100 in accordance with various embodiments of the presentdisclosure. Telecommunication routing system 100 includes a host network102, a remote network 104, and a public switched telephone network(PSTN) 106 connected to the host network 102 via a media gateway 130. Acommunications device 108, such as an analog phone, is communicablycoupled with PSTN 106. PSTN is communicably coupled with host network102, and host network 102 is communicably coupled with remote network104. Remote network 104 is communicably coupled with communicationdevices 114, and 116. Host network 102 includes a host routing device110, a database 122, and an application server 140. Database 122 may becommunicably coupled to host routing device 110 and application server140. Host network 102 is further communicably coupled with acommunication device 118.

Host routing device 110 assists with the routing of calls in the VoIPnetwork 102. Routing is facilitated by tags provided to host routingdevice 110 and the tags may be provided by an application server 140.Application server 140 may be a network service computing device and mayinclude one or more servers, mainframes, mobile devices, laptopcomputers, tablets, video streaming devices, smart televisions,smartphones, web appliances, communication network nodes (e.g., networkrouters, switches, or bridges), or computing systems embedded withinanother device or system. Application server 140 assists host routingdevice 110 with the creation and maintenance of tags for various VoIPlines.

Remote network 104, which may include at least one remote switch, servesone or more communications devices, e.g., communication devices 114,116. Communications device 114 may be associated with a first telephonenumber (TN1), and communications device 116 may be associated with asecond telephone number (TN2), for example. When a call is made fromcommunication devices 114 or 116 to an outside communications device,such as communications device 108 and/or communications device 118, thecall passes through host routing device 110 of host network 102 andremote network 104 with host network 102 assisting with routing of thecalls made from communication devices 114 or 116.

Database 122 may be a location tag identifier database for storing aplurality of tags 208 corresponding to a plurality of VoIP phone lines204. An exemplary portion 200 of data from database 122 is illustratedin FIG. 2. Portion 200 of database 122 includes a plurality of datafiles 202 with each file including a VoIP line 204, a telephone number(TN) 206, a tag 208, a geographic location geo-location 210 associatedwith the tag 208, and a billing number 212.

A tag 208 may be a unit of information used as a label or marker for thefile 202. In some embodiments, a tag 208 is a string or set ofcharacters comprising software code that identifies various conditionsabout data in a file 202 and may be located in, e.g., a header of thefile 202. Tags 208 are assigned to VoIP lines 204 to specify routing andbilling protocols for calls made from the VoIP lines 204. Tags 208specify specific and updated geographical locations 210 associated withthe VoIP lines 204 managed by host network 102. Tags 208 may furtherdefine a billing number 212 for a VoIP line 204. The telephone number(TN) 206 of each file 202 may be a standard NANP number.

Tags 208 may be specific to particular building numbers of a customer ofhost network 102. More particularly, a tag 208 may be associated with aspecific building within a campus. Assigning tags 208 to particularbuildings within a campus allows for better management of VoIP lines bygrouping one or more VoIP lines to a building.

Geographic location 210 may include an exact street or postal addressincluding a building number for the VoIP line 204. In some embodiments,geographic location 210 may include a master street address guide (MSAG)address. An MSAG address defines a very specific physical location. Forexample, a standard postal address may define a particular building orset of buildings. In contrast, an MSAG address defines a more specificlocation, e.g., a particular building in a campus.

In some embodiments of the present disclosure, when the owner of remotenetwork 104 is setting up a plurality of VoIP lines for, e.g.,communication devices 114 and 116, tags 208 can be assigned to each ofthe VoIP lines. As such, upon implementation of such VoIP lines atremote network 104, host routing device 110 is provided with validgeographical information about where the communication devices 114 and116 are going to be utilizing one or more VoIP lines. For example, VoIPline 1 of FIG. 2 may be accessible via communication device 114 and maybe assigned a New York phone number of “212-222-2222.” In addition, VoIPline 1 may be assigned a tag, e.g., “TAG A,” which specifies that VoIPLine 1, via communication device 114, is being operated and/or accessedout of Denver (and not New York), and that VoIP Line 1 is assigned“Billing Number #10.” TAG A may be assigned to VoIP Line 1 upon theimplementation (set-up or provisioning of VoIP lines to a remotenetwork) of VoIP Line 1 at remote network 104. Alternatively, TAG A (andthe associated geographical location 210 and billing number 212) may beassigned to VoIP Line 1 in database 122 after implementation of VoIPLine1. In further embodiments, a user operating VoIP Line 1 may desireto move from Denver, Colo. to another location, such as Dallas, Tex. inthe example here. Accordingly, TAG A of VoIP Line 1 may be replaced withanother tag reflective of the change in location, e.g., TAG B, so thatthe host routing device 110 and the application server 140 can adjustrouting functionality for calls made from VoIP line 1. Specifically,consistent with the instant example, when a caller moves to Dallas thecaller can maintain the same VoIP line 1 by switching tags. Suchflexibility is achievable because according to the present disclosure,telephone numbers 206 associated with a given VoIP line 204 may beignored by the network for purposes of routing functionality withrouting functionality instead defined by tags 208.

Billing numbers 212 assist the telecommunication routing system 100 withthe proper billing procedures for calls made from VoIP lines 204 basedupon the tags 208 and geographical information 210. In some embodiments,the tag 208 gets used, or is translated to the billing number 212 ascalls are routed through the telecommunications routing system 100. Tags208 determine whether calls are designated as local, or long distance.As such, the dialable TNs 206 become irrelevant with respect to routingand billing. Tags 208 and billing numbers 212 are compatible acrossvarious network elements and components such that tags 208 and billingnumbers 212 may be seamlessly integrated within or accessible by all thenetwork components, carriers, and networks, which need the information,of telecommunications routing system 100. Compatible, in someembodiments means that the tags 208 and billing numbers 212 can traversewith the data defining a call through numerous different networkswithout requiring additional software or systems to interpret tags orbilling numbers. For example tags 208 and billing numbers 212 can becompatible with SIP and SS7 environments. In some embodiments, tags 208are received by outside carriers of host network 102 as merely billingnumbers 212. Tags 208 provide a flexible way to bill and route calls ina VoIP network without requiring modification of systems by outsidecarriers or network elements of telecommunications routing system 100.Namely, tags 208 facilitate accurate routing and billing of calls fromVoIP callers in a VoIP network but do not require networks external tohost network 102 to update software or systems in order for calls to beaccurately routed to such external networks.

In some embodiments, the host routing device 110, ignores the TN, andassigns tags to govern the routing functionality for each VoIP linepreviously defined by the TNs 206, e.g., the functionality or routingparameters may be defined by the tags 208. Routing parameters define howcalls made from VoIP lines are routed through a network.

Alternatively, such tag integration can be achieved alone or incombination with the application server 140. More specifically, in someembodiments, application server 140, using a software application suchas a tag maintenance application 750, can maintain and manage a routingtable in database 122 with a plurality of tags 208; the tags associatedwith one or more VoIP lines 204. As calls need to be routed through hostnetwork 102, the application server 140 may instruct or aide hostrouting device 110 by communicating how calls for particular VoIP linesshould be routed. In one specific example, if a caller initiates a callwhich is received by host routing device 110, and the caller is using aVoIP line 204 associated with a particular tag 208, either the hostrouting device 110 or the application server 140 may receive or identifythe tag 208 as the call is received at the host routing device 110, theapplication server 140 can query database 122 for information about thetag 208, and the call can be accurately routed to a network external tohost network 102 based on information associated with the tag 208 (suchas the geo-location 210 of the VoIP line).

In some embodiments, billing numbers 212 are attached to specificgeographic locations 210 and may be assigned to specific customerlocations or buildings. Billing numbers 212 assist with the computationof costs per call based on the geographic information 210 assigned toeach of the VoIP lines 204. In some embodiments, tags 208 may bereplaced with billing numbers 212 as calls are routed outside of thehost network 102.

The creation of files 202 and associated file data, and the creation andmaintenance of tags 208 can be implemented and processed by one or moreprocessors of application server 140 with relevant data stored indatabase 122. The files and tag information may be made available tohost routing device 110 to facilitate improved routing of VoIP calls. Inother embodiments, a plurality of application servers 140 and aplurality of databases 122 may be utilized for the maintenance of tags208. Further, database 122 may be external to host network 102 such thatapplication server 140 communicates with database 122 remotely to storeand access tags 208.

As shown in FIGS. 2 and 5-6, using one or more software applicationsexecuted by application server 140, each of the telephone numbersassociated with a plurality of VoIP lines can, for the purposes ofrouting, be ignored. In other words, the VoIP lines 204 maintain thetelephone numbers 206 for each VoIP line from an end user perspective,but the tags 208 may replace the telephone numbers 206 for VoIP lines204 with respect to routing functionality. As such, when host routingdevice 110 is requested to connect a call between communication device116 and another communication device, host routing device 110 identifiesthe physical location of communication device 116, for routing andbilling purposes, depending on tags 208, and does not merely applyinformation from the telephone number 206 assigned to communicationdevice 116.

Returning to FIG. 3, exemplary signaling information 300 is illustratedaccording to some embodiments of the present invention. FIG. 3specifically demonstrates exemplary signaling information for when acaller of a first remote network such as remote network 104, initiates acall to a recipient of a different remote network and each of the callerand recipient VoIP lines have been assigned tags. In the presentexample, host network 102 and host routing device 110 manage traffic forthe remote networks. The remote networks are both considered to becustomers (and may be separate customers) of host network 102.

Although call signaling information 300 may often comprise moreinformation than shown in FIG. 3, a first field, the caller informationfield 302, may be populated by the caller telephone number (TN) 306 aand a caller tag 308 a. A second field, the recipient information field304, may be populated by the recipient TN 306 b and the recipient tag308 b. Field 302, field 304, and their respective contents aide areceiving device, such as host routing device 110, in routing the callto the proper destination, or target, such as a remote switch of remotenetwork 104.

While FIG. 3 depicts multiple users each having a tag of the presentdisclosure, in some embodiments, one or more of the caller or therecipient of the call may be a party outside of remote network 104 orhost network 102 such as a user of communication device 108. Suchexternal phone lines may still be routed based upon telephone numbersand will not have a tag 208. Thus, signaling information 300 passingthrough and managed by host routing device 110 may include one or moretags 208 or may include a single tag depending upon the parties to theparticular call.

Signaling information 300 may be communicated between network signalingelements in a communications system, such as telecommunication routingsystem 100, via different methods, such as, for example, SS7, PRI, CAS,and SIP. SIP signaling is a unique VoIP signaling protocol and may beparticularly useful for signaling by host network 102.

FIG. 4 illustrates the difference in routing when using tags 208 of thepresent disclosure as opposed to routing VoIP calls using traditionalNANP telephone numbers. In FIG. 4, call routing is specificallydemonstrated showing calls made near a boundary 402 between two LATAs,LATA 1, and LATA 2. In the example of FIG. 4, LATA 1 happens to be inColorado, and LATA 2 happens to be in Arizona, but such geographicreferences are made merely as an example to illustrate the describedconcepts. Calls are routed using host routing device 110 and remoteswitches 450 and 460. For the example in FIG. 4, it should be assumedthat calls crossing the boundary 402 are designated as long distancecalls.

FIG. 4 further illustrates two separate VoIP communication devices 410and 412, using separate respective VoIP lines. Communication device 410is operating a VoIP line with an Arizona telephone number (TN).Communication device 412 is operating a VoIP line using a Colorado TN.Importantly, communication devices 410 and 412 are physically close toone another such that the devices share a common local calling area 420,i.e., calls between communication devices 410 and 412 should be “local”for billing purposes and a local trunk should be established between thecommunication devices when calls are made between the communicationdevices 410 and 412. At the same time, if calls are routed throughboundary 402, the calls should be designated as long distance, orinter-LATA calls and long distance communication pathways should beestablished.

Without the tags 208 of the present disclosure, calls made from thecommunication devices 410 and 412 may be routed according to the TNnumber. As such, calls may pass through communication paths 422 and 424which includes passing through boundary 402. In contrast, utilizing tags208 of the present disclosure, calls made from communication devices 410and 412 are properly routed through communication paths 432 and 434,within the local calling area 420. Tags 208 further facilitate suchcalls, being routed between communication devices 410 and 412 via localcommunication paths 432 and 434, to be billed as local calls.

FIG. 5 depicts an exemplary flow diagram 500 illustrating methods forassigning and modifying tags for VoIP lines. In block 502, anapplication server 104 of host network 102 receives a request toprovision a plurality of VoIP lines for a remote network, such as remotenetwork 104. The request may be received by, e.g., a portal 18. A portal18 may comprise a web interface to allow users of VoIP lines to updategeographic information for the VoIP lines. More specifically, a user canlog onto a web page via a computing system 24 and access the portal 18.Portal 18 may further comprise at least one application programinterface (API) that sits behind a web interface to provide additionalfunctionality and features. In some embodiments, portal 18 is accessibleto the user via a mobile or general software application downloaded oraccessible on a computing system or communication device such ascommunication device 114. The computing systems 24 may include mobilephones (similar to communication devices 114 and 116), smartphones,servers, mainframes, laptop computers, tablets, smart televisions, orsmartphones.

The request may specify that various physical locations be assigned toone or more of the VoIP lines. For example, referring to a VoIP linewith a “212” area code, it may be requested from the remote network 104that the VoIP line be associated with a geographic location in Denver,Colo. In some embodiments, a plurality of VoIP lines are designated witha particular building of a customer and associated with a particulargeographic location of the customer. According to some embodiments ofthe present disclosure, a customer (remote network 104) obtains a blockof VoIP lines associated with a block of TNs and allocates the TNs toits customers or users.

More specifically, according to some embodiments of the presentdisclosure, when a customer of host network 102, such as the owner ofremote network 104, is set up according to the telecommunicationsrouting system 100 illustrated in FIG. 1, the customer begins byacquiring a VoIP switch that may serve as a remote switch, such as aclass 5 switch. Setting up a remote network 104 may include purchasingaccess to host network 102 and purchasing a plurality of VoIP lines inaddition to the deployment of network components to allow remote networkto function as a network for the VoIP lines and communicate with othernetworks such as host network 102. The customer, remote network 104, mayacquire telephone numbers from the provider of host network 102. Thehost network 102 then provides access to computing systems of the hostnetwork 102 to allow the customer to provision against the host network102 for utilizing host routing device 110 and/or other host switches.For each of the telephone numbers acquired by the customer, the customerdesignates an intended location where the telephone numbers will beused. Such information may be referred to as geographic information,locations, or the like.

In block 506, a first set of tags, such as tags 208, are created for andassigned to each of the VoIP lines based upon the requested geographiclocations received from remote network 104. Tags 208 are associated witha geographic location 210 and a billing number 212. In some embodiments,tags 208 may populate the one or more routing parameters instead ofusing information from telephone numbers. Using tags 208, the telephonenumbers associated with each of the VoIP lines are ignored with respectto routing functionality. In other words, routing functionality for eachof the VoIP lines is no longer based on the telephone numbers associatedwith the VoIP lines. The telephone numbers may remain unchanged, but therouting functionality is improved by use of the tags which areretrofitted with up-to-date geographic information about where the VoIPlines are being operated. As such, tags 208 provide more accuraterouting of VoIP calls while maintaining the status quo with respect toassignment of telephone numbers.

In block 508, host network 102 may receive a request from one or morecommunication devices associated with one or more VoIP lines to updategeographic information associated with the one or more VoIP lines. Auser of a VoIP line may decide to move to a different physical locationbut may also wish to maintain the same telephone number for the VoIPline.

In some embodiments, a user of a VoIP line can send the request toupdate geographic information associated with the VoIP line via a portalsimilar to portal 18. As discussed above, portal 18 may comprise a webinterface to allow users of VoIP lines to update geographic informationfor the VoIP lines. More specifically, a user can log onto a web pagevia a computing system 24 and access the portal 18. Portal 18 mayfurther comprise at least one application program interface (API) thatsits behind a web interface to provide additional functionality andfeatures. In some embodiments, portal 18 is accessible to the user via amobile or general software application downloaded or accessible on acomputing system or communication device such as communication device114. The computing systems 24 may include mobile phones (as in the caseof communication devices 114 and 116), smartphones, servers, mainframes,laptop computers, tablets, smart televisions, or smartphones.

As part of initiating a request to update geographic information, an enduser can be prompted to provide a postal address. The postal address maybe processed by a geographic information system (GIS) system of hostnetwork 102. GIS validates the postal address to ensure that the postaladdress is an actual recognizable address. As such, GIS ensures thatvalid geographic information is being received from the end user.

Finally, in block 510, when the new geographic information has beenreceived and validated, the tags associated with the one or more VoIPlines can either be replaced or modified to reflect the new geographicinformation. Thus, telecommunications routing system 100 ensures thatcalls routed across host network 102 are routed using optimized routingparameters, e.g., updated geographic information as specified in thetags.

FIG. 6 depicts a flow diagram 600 illustrating methods for routing VoIPcalls using a host routing device 110 and a plurality of tags, accordingto various embodiments of the present invention. Host routing device 110utilizes tags 208 to determine proper routing protocols. In block 602, acall may be sent from a user of remote network 104 to, e.g., a user ofPSTN 106 such as communication device 108. The call may be initiated by,for example, communication device 114.

In block 604, a determination is made whether the calling number hasbeen assigned a tag 208, which may involve querying database 122 todetermine proper call routing. In cases where a tag 208 is present,routing of the call from the communication device 114 to thecommunication device 108 may be based on the tag 208 and associated datasuch as geographic information 210. If a tag 208 is not present, thenrouting to a remote switch and to the communication device 108 may bebased on the TN field 206 (also known as the calling party numberfield).

In some embodiments, where a tag 208 is assigned to the calling number,one or more of the host routing device 110 or application server 140 mayidentify the tag 208, and retrieve geographic location information 210associated with the tag 208 as stored in database 122. Thereafter, thehost routing device 110, using the geographic location information 210,can properly route the call to its intended destination. In someembodiments, the tag 208 is attached to a data stream associated withthe call along with the billing number 212 and travels through externalnetworks to a recipient. In some embodiments, the tag 208 does nottravel with the call (data stream) once the host routing device 112sends the call outside of host network 102 and is used by host routingdevice 110 merely to define routing functionality for calls made fromhost network 102.

In block 606, the call is routed based on a tag assigned to the VoIPline and associated with the communication device 114. Finally, the callfrom communication device 114 to communication device 108 is billedbased upon the information provided by the tag 208. In some embodiments,the tag 208 gets used, or is translated to the billing number 212 as thecall is routed through telecommunications routing system 100 from thecommunication device 114 to the communication device 108. Tag 208determines whether the call from communication device 114 tocommunication device 108 is a local, or long distance call. As such, thedial-able TN 206 associated with the communication device 114 is ignoredwith respect to routing and billing. The tag 208 and billing number 212are both compatible across various network elements and components suchthat tags 208 and billing numbers 212 are seamlessly integrated withintelecommunications routing system 100. For example, tags 208 and billingnumbers 212 can be compatible with SIP and SS7 environments. In someembodiments, the tag 208 of the present example is received by outsidecarriers of host network 102 as a billing number 212. The tag 208provides a flexible way to bill and route calls from communicationdevice 114 without requiring modification of systems by outside carriersof host network 102.

In some embodiments, host network 102 may be further communicablycoupled with a Local Exchange Routing Guide, such as, for exampleTelcordia® LERG™ Routing Guide (“LERG”) database (not shown), and with aNumber Portability Administration Center (“NPAC”) database (not shown).According to some embodiments of the present invention, a LERG databaseis a Telcordia® LERG™ Routing Guide, which may be produced and/or outputby a Telcordia® Business Integrated Rating and Routing Database System(BIRRDS).

Host network 102 and remote network 104 may include any system capableof passing communications from one entity to another such as, e.g., theInternet, a virtual private network, a local area network, a wide areanetwork, a Wi-Fi network, a PSTN, a cellular network, or any combinationthereof. “Communicably coupled,” as used herein, includes any means ofcoupling whereby information is passed, such as, e.g., electricallycoupled by a wire, optical cable, or wirelessly coupled by a radiofrequency or any such wireless media and may include both directcoupling and indirect coupling. Routing includes any action taken totransfer, initiate, terminate, end, and/or direct calls and/or data.Communication devices 114, 116, and 118 may be end user communicationdevices and may include IP-enabled telephones, cellular telephones,laptop computers, fax machines, or the like.

Remote network 104 may be a private network such as a customer networkof host network 102. The communication and networking components ofremote network 104 enable a user at the remote network 104 tocommunicate via the host network 102 with other communication devices,such as another user via communication device 108. In some embodiments,remote network 104 may connect to the host network 102 via a sessionborder controller (SBC) device or Network Address Translation (NAT)device which in some embodiments may be included as part of host routingdevice 110. In general, an SBC is a device deployed within the hostnetwork 102 to control signaling involved in setting up and tearing downcommunications between an end user and the host network 102. In someembodiments, host routing device 110 may include a plurality of SBCsutilized in host network 102.

In some embodiments, host routing device 110 may be communicably coupledwith application server 140. Application server 140 may, via aprocessor, execute one or more software applications and communicatewith host routing device 110 to assist with tag generation, tagmaintenance, and routing. Application server 140 may further becommunicably coupled with database 122.

Communication device 106 accesses, and is accessed by the host network102 via PSTN 106 and a local exchange carrier (LEC) (not shown).Communication via any of the networks may be wired, wireless, or anycombination thereof. Additionally, the PSTN 106 may communicate with thehost network 102 through a media gateway device 130.

According to some embodiments of the present invention, host network 102is a VoIP network, and host routing device 110 is a network routingresource. Embodiments of the present disclosure permit remote network104 to serve users by connecting to PSTN 106 and/or other networksthrough host network 102.

As a network routing resource, host routing device 110 may include anydevice capable of routing a call and/or data and can include one or moreof a switch, a session border controller (SBC), a gateway, a gatewaycontroller, a softswitch, a proxy server or a feature server. Hostrouting device 110 may further include, for example, a Class 5softswitch, a Class 4 softswitch, or a hybrid Class 4/Class 5softswitch, which has all or some of the properties and functions of aClass 4 softswitch and/or a Class 5 softswitch. In some embodiments,host routing device 110 comprises a bundle of networking components andincludes one or more switches in addition to application server 140 anddatabase 122.

In one embodiment, host routing device 110 includes a session bordercontroller (SBC) and a gateway media device. In such an embodiment, oneor more trunk connections may connect the SBC and a border media gatewaydevice to host network 102. In general, a trunk is a transmissionchannel between two points, typically between two networks to carrycommunications between the networks. In an Internet Protocol (IP)environment, the trunks provide the IP interconnect between an SBC andthe host network 102. To facilitate interconnect, one or more IPaddresses are shared between the SBC and host network 102. The IPaddresses allow for the communications transmitted between the SBC andhost network 102 to be addressed and sent to the correct network device.In addition, several trunks may be connected to the SBC such that theSBC may receive communication from several customers to the host network102. One or more of the application server 140, host routing device 110,and SBC may provide telecommunication services to and from communicationdevices 114, 116, and 106. For example, in one embodiment, applicationserver 140 can assist with calls and services to a proper end userthrough a trunk group connection and an SBC.

Remote network 104 may include a private branch exchange (PBX), anIP-PBX, IP-phones, and an SBC. Remote network 104 may include a remoteswitch, for example, a Class 5 switch. The Class 5 switch may be, forexample, a Class 5 softswitch which is capable of converting a networksignaling format to a media gateway and call session control format. AClass 5 softswitch can utilize the signaling to establish and teardownuser calls and invoke call features on existing calls, to providevarious end-user services. A Class 5 softswitch may further provide forcall accounting intelligence for a host network. A Class 4 softswitch,on the other hand, may in some embodiments perform higher-levelswitching and routing tasks while not necessarily performing the samecall features that a Class 5 softswitch performs, such as, for example,caller ID. Class 4 softswitches are often situated closer to the centerof the network and configured to handle VoIP calls in a fashion similarto that of tandem office switches in circuitswitched networks. A hybridClass 4/Class 5 softswitch includes some or all of the properties andfunctions of a Class 4 softswitch and/or a Class 5 softswitch, accordingto embodiments of the present disclosure.

FIG. 7 is an example schematic diagram of a computing system 700 thatmay implement various methodologies discussed herein. For example, thecomputing system 700 may comprise the application server 140 used toexecute one or more software applications and assist with tag creationand maintenance and routing of VoIP calls with host switch 110, or, itmay comprise a computing system used by end users to communicate withapplication server 140 and update geographic information for VoIP lines.The computing system 700 includes a bus 701 (i.e., interconnect), atleast one processor 702 or other computing element, at least onecommunication port 703, a main memory 704, a removable storage media705, a read-only memory 706, and a mass storage device 707. Processor(s)702 can be any known processor, such as, but not limited to, an Intel®Itanium® or Itanium 2® processor(s), AMD® Opteron® or Athlon MP®processor(s), or Motorola® lines of processors. Communication port 703can be any of an RS-232 port for use with a modem based dial-upconnection, a 10/100 Ethernet port, a Gigabit port using copper orfiber, or a USB port. Communication port(s) 703 may be chosen dependingon a network such as a Local Area Network (LAN), a Wide Area Network(WAN), or any network to which the computer system 200 connects.Computing system may further include a transport and/or transit network755, a display screen 760, an I/O port 740, and an input device 745 suchas a mouse or keyboard.

Main memory 704 can be Random Access Memory (RAM) or any other dynamicstorage device(s) commonly known in the art. Read-only memory 706 can beany static storage device(s) such as Programmable Read-Only Memory(PROM) chips for storing static information such as instructions forprocessor 702. Mass storage device 707 can be used to store informationand instructions. For example, hard disks such as the Adaptec® family ofSmall Computer Serial Interface (SCSI) drives, an optical disc, an arrayof disks such as Redundant Array of Independent Disks (RAID), such asthe Adaptec® family of RAID drives, or any other mass storage devices,may be used.

Bus 701 communicatively couples processor(s) 702 with the other memory,storage and communications blocks. Bus 701 can be a PCI/PCI-X, SCSI, orUniversal Serial Bus (USB) based system bus (or other) depending on thestorage devices used. Removable storage media 705 can be any kind ofexternal hard drives, thumb drives, Compact Disc-Read Only Memory(CD-ROM), Compact Disc-Re-Writable (CD-RW), Digital Video Disk-Read OnlyMemory (DVD-ROM), etc.

Embodiments herein may be provided as a computer program product, whichmay include a machine-readable medium having stored thereon instructionswhich may be used to program a computer (or other electronic devices) toperform a process. The machine-readable medium may include, but is notlimited to optical discs, CD-ROMs, magneto-optical disks, ROMs, RAMs,erasable programmable read-only memories (EPROMs), electrically erasableprogrammable read-only memories (EEPROMs), magnetic or optical cards,flash memory, or other type of media/machine-readable medium suitablefor storing electronic instructions. Moreover, embodiments herein mayalso be downloaded as a computer program product, wherein the programmay be transferred from a remote computer to a requesting computer byway of data signals embodied in a carrier wave or other propagationmedium via a communication link (e.g., modem or network connection).

As shown, main memory 704 may be encoded with a tag maintenance softwareapplication 750 that supports functionality as discussed above and asdiscussed further below. For example, in one embodiment, the tagmaintenance software application 750 may include or otherwise implementsoftware functions to create and maintain tags for VoIP lines.Alternatively, where computing system 700 represents an end user system,the software application 750 may comprise a portal for allowing an enduser to update geographical location corresponding to a VoIP line. Thetag maintenance software application 750 (and/or other resources asdescribed herein) can be embodied as software code such as data and/orlogic instructions (e.g., code stored in the memory or on anothercomputer readable medium such as a disk) that supports processingfunctionality according to different embodiments described herein.During operation of one embodiment, processor(s) 702 accesses mainmemory 704 via the use of bus 701 in order to launch, run, execute,interpret or otherwise perform processes, such as through logicinstructions, executing on the processor 702 and based on the tagmaintenance software application 750 stored in main memory or otherwisetangibly stored.

The description above includes example systems, methods, techniques,instruction sequences, and/or computer program products that embodytechniques of the present disclosure. However, it is understood that thedescribed disclosure may be practiced without these specific details. Inthe present disclosure, the methods disclosed may be implemented as setsof instructions or software readable by a device. Further, it isunderstood that the specific order or hierarchy of steps in the methodsdisclosed are instances of example approaches. Based upon designpreferences, it is understood that the specific order or hierarchy ofsteps in the method can be rearranged while remaining within thedisclosed subject matter. The accompanying method claims presentelements of the various steps in a sample order, and are not necessarilymeant to be limited to the specific order or hierarchy presented.

The described disclosure may be provided as a computer program product,or software, that may include a machine-readable medium having storedthereon instructions, which may be used to program a computer system (orother electronic devices) to perform a process according to the presentdisclosure. A machine-readable medium includes any mechanism for storinginformation in a form (e.g., software, processing application) readableby a machine (e.g., a computer). The machine-readable medium mayinclude, but is not limited to, magnetic storage medium (e.g., opticalstorage medium (e.g., CD-ROM); magneto-optical storage medium, read onlymemory (ROM); random access memory (RAM); erasable programmable memory(e.g., EPROM and EEPROM); flash memory; or other types of mediumsuitable for storing electronic instructions.

It is believed that the present disclosure and many of its attendantadvantages should be understood by the foregoing description, and itshould be apparent that various changes may be made in the form,construction and arrangement of the components without departing fromthe disclosed subject matter or without sacrificing all of its materialadvantages. The form described is merely explanatory, and it is theintention of the following claims to encompass and include such changes.

While the present disclosure has been described with reference tovarious embodiments, it should be understood that these embodiments areillustrative and that the scope of the disclosure is not limited tothem. Many variations, modifications, additions, and improvements arepossible. More generally, embodiments in accordance with the presentdisclosure have been described in the context of particularimplementations. Functionality may be separated or combined in blocksdifferently in various embodiments of the disclosure or described withdifferent terminology. These and other variations, modifications,additions, and improvements may fall within the scope of the disclosureas defined in the claims that follow.

What is claimed is:
 1. A method of call routing for Voice over InternetProtocol (VoIP) calls, comprising: utilizing a network service computingdevice comprising at least one memory for storing instructions that areexecuted by at least one processor to perform the operations of:receiving a first location associated with a first VoIP line, the firstVoIP line including a telephone number associated with the first VoIPline; creating a first tag associated with the first location, the firsttag including geographical information associated with the firstlocation to facilitate routing functionality for calls made from thefirst VoIP by the geographic information instead of routing calls fromthe first VoIP line by the telephone number; receiving a request tofacilitate a VoIP call between the first VoIP line and a second VoIPline; and routing the VoIP call using the first tag by a host routingdevice coupled to the network service computing device.
 2. The method ofclaim 1, further comprising generating a first billing number associatedwith the first tag to specify accurate billing of calls made from thefirst VoIP line.
 3. The method of claim 1, further comprising validatingthe first location to be a known valid address.
 4. The method of claim1, further comprising receiving the first location via a portal, webinterface, mobile application, instant messaging application, orApplication Programming Interface (API).
 5. The method of claim 1,wherein the first location is associated with a first local access andtransport area (LATA).
 6. The method of claim 1, further comprisingreceiving a request to update the geographical information associatedwith the first VoIP line and the first tag.
 7. The method of claim 6,further comprising receiving a second location associated with a secondlocal access and transport area (LATA).
 8. The method of claim 7,further comprising coupling a second tag to the first VoIP line basedupon the second location such that calls are routed from the first VoIPline utilizing the second tag.
 9. A telecommunications routing systemfor routing Voice over Internet Protocol (VoIP) calls over a hostnetwork, comprising: a host routing device; and a network servicecomputing device coupled to the host routing device, the network servicecomputing device comprising at least one memory for storing instructionsthat are executed by at least one processor to: receive a first locationassociated with a first VoIP line; and create a first tag for the firstVoIP line based upon the first location; wherein the host routing deviceroutes calls from the first VoIP line based upon the first tag.
 10. Thesystem of claim 9, wherein the host routing device includes at least oneswitch.
 11. The system of claim 9, further including a remote networkcommunicably coupled to the host network.
 12. The system of claim 11,wherein the first VoIP line is associated with a first communicationdevice of the remote network.
 13. The system of claim 9, wherein thefirst location includes a postal address where the first VoIP line isbeing utilized.
 14. A method of call routing for Voice over InternetProtocol (VoIP) calls, comprising: utilizing a network service computingdevice comprising at least one memory for storing instructions that areexecuted by at least one processor to perform the operations of:receiving a first location associated with a first VoIP line; andgenerating a first tag associated with the first location to specifyrouting functionality for calls made from the first VoIP line.
 15. Themethod of claim 14, wherein a telephone number associated with the firstVoIP line is ignored with respect to the routing functionality becauseof the first tag.
 16. The method of claim 14, further comprisingassigning a billing number to the first VoIP line based on the firsttag.
 17. The method of claim 14, further comprising: receiving a secondlocation associated with the first VoIP line; and updating the first tagwith a second tag associated with the second location for purposes ofcall routing from the first VoIP line.
 18. The method of claim 14,further comprising: receiving a request to facilitate a VoIP callbetween the first VoIP line and a second VoIP line; and routing the VoIPcall using the first tag.
 19. The method of claim 14, further comprisingreceiving the location from a customer of the telecommunications networkvia a portal, web interface, mobile application, instant messagingapplication, or Application Programming Interface (API).
 20. The methodof claim 14, wherein a telephone number associated with the first VoIPline is associated with a local calling area that is different from asecond local calling area associated with the location.